The latest release information about the Web Forms for Marketers module version 2.1.
1. Release History
Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.
September 30, 2010
The Web Forms for Marketers module 2.1.0 rev.100920 is released.
This release is designed to work with Sitecore CMS 6.2 and Sitecore CMS 6.3 or later and Sitecore OMS 1.0.1 or later.
Tested with Sitecore CMS 6.2.0 rev. 100507, 6.3.0 rev.100830.
Please visit the appropriate Module Upgrade section for instruction how to upgrade the module.
Change log.
Issues Resolved:
- The "Subscribe to Target Audience" save action might not work with some field types. (332475)
- The Path to Success Page was parsed incorrectly when the linkManager >> languageEmbedding setting in web.config was set to 'always' (332637)
- In the “Create user” save action, the form field that is used as a source for User Password was not shown (332475)
- In some cases Global sessions could be shared between visitors so that form analytics information was shown for the incorrect visitor (333331)
- Submitting a form could throw an exception to log file if the “Redirect to the page” option was chosen as a success action (332067)
- When using Web Forms for Marketers 2.1.0 rev.100806 with Sitecore 6.2, dropouts tracking may not work correctly and an exception occurred in the log file. (332855)
August 13, 2010
The Web Forms for Marketers module 2.1.0 rev.100806 is released.
This release is designed to work with Sitecore CMS 6.2 and Sitecore CMS 6.3 or later.
Tested with Sitecore CMS 6.2.0 rev. 100617 and 6.3.0 rev.100716.
Please visit the appropriate Module Upgrade section for instruction how to upgrade the module.
The previously released update Web Forms for Marketers 2.1.0 rev. 100804 was designed to work only with Sitecore CMS 6.3. The 2.1.0 rev. 100806 (Update 2) release supersedes the 2.1.0 100804 (Update 1) release. If you have downloaded Web Forms for Marketers 2.1.0 rev. 100804 and wish to upgrade to Web Forms for Marketers 2.1.0 rev. 100806 please contact Customer Service.
Change log.
- Added support for versions of Sitecore CMS 6 earlier than CMS 6.3
- Events in the Detailed usability report are shown in an incorrect sequence when Robot Attack Protection is enabled (332260)
August 6, 2010
The Web Forms for Marketers module 2.1.0 rev.100804 is released.
This release is designed to work with Sitecore CMS 6.3.0 or later. A future update will provide compatibility with earlier versions of Sitecore CMS 6.
Tested with Sitecore CMS 6.3.0 rev.100716.
Please visit the appropriate Module Upgrade section for instruction how to upgrade the module.
Change log.
New features:
- Subscribe to Target Audience save action:
- Target audiences are used by the Email Campaign Manager to store distribution lists which are used to send emails. This save action subscribes the visitor to target audiences or unsubscribes them from target audiences.
- This save action can be used independently or in conjunction with the Send Standard Message Save Action.
- The Subscribe to Target Audience save action also gives users the option to use the Email Campaign Manager’s ability to send a confirmation mail to visitors, which contains a link. When this link is clicked the subscription is then activated. This type of confirmation is a legal requirement in some countries.
- A sample “Get Our Newsletter” form has been added which shows an example of how the Subscribe to Target Audience action may be used.
- Robot Attack Protection:
- The current Captcha field has been extended so that the user now has the option to show the Captcha field only under certain conditions or combination of conditions. This can help to protect against robot attacks which submit forms multiple times while causing minimal disturbance to the user experience for genuine visitors.
- The Captcha field can be displayed in cases where Sitecore has identified a visitor a robot.
- The Captcha field can be displayed in cases where a suspicious visitor is detected. Suspicious visitors can be defined by users, as visitors who have submitted the same form a specific number of times, in a specific number of minutes.
- The Captcha field can be displayed in cases where suspicious form activity is detected. Suspicious form activity can be defined by users by designating a specific number of times the same form has been submitted on the site in specific number of minutes.
- Users have the ability to decide, depending on the conditions under which the Captcha field is displayed, whether to display the form with the Captcha field on the same page as the form normally appears, or on a different page. Users can also customize the error messages that appear on these pages.
- Users can configure a warning mail to be sent to specific people if a suspicious visitor or suspicious form activity is detected.
Issues Resolved:
- Several issues which caused compatibility problems with Sitecore CMS 6.3.0 have been resolved (331069)
- The ComponentArt.WebUI.dll library was updated in Sitecore CMS 6.3. Web Forms for Marketers 2.1 contained references to the previous version of the library.
- The Newtonsoft.Json.dll library was updated in Sitecore CMS 6.3. Web Forms for Marketers 2.1 contained references to the previous version of the library.
- The Sitecore.SQLite.dll and System.Data.SQLite.dll libraries were removed in Sitecore CMS 6.3. Web Forms for Marketers 2.1 contained references to these. The required portions of the Sitecore.SQLite.dll library have been included in the Web Forms for Marketers library and the System.Data.SQLite.dll has be included in the Web Forms for Marketers package.
- An issue which caused users who were members of the Sitecore Client Forms Author role to be unable to edit forms using the Page Editor has been resolved. (330910)
- An issue which caused forms not to be correctly submitted if the id of the form tag in the layout was not “mainform” has been resolved. (332081)
- An issue which meant that forms that did not contain any fields and had analytics disabled caused a javascript error has been resolved. (332123)
July 1, 2010
The Web Forms for Marketers module 2.1.0 rev.100629 is released.
Tested with Sitecore CMS 6.2.0 rev.100507 (Update 2).
Please visit the appropriate Installation Guide section for instruction how to install the module.
Change log.
New features:
- Localization and Targeted Error Messages:
- Localized list fields - List fields and the items contained in them can now be fully localized. An item can have a single value for statistical purposes but be displayed in multiple languages. The value / text concept can also be used for more complex integration purposes.
- Success localization – the Success Action is now able to be localized in multiple languages.
- Build lists with queries - Previously list items could be created manually or populated using Sitecore items, You can now use various types of queries to create list items from different parts of your content tree, including Sitecore query, fast query and XPath query.
- Targeted Error Messaging – All fields which have a regular expression validation can have localized error messages on a per field basis. This allows the marketer to dictate exactly what error messages the visitor will see in each failure scenario in each language.
- Submit Action Error Messaging - Individual Submit Actions on individual forms can be configured with individual error messages for each form in every language.
- New Submit Actions:
- Conditional rules to trigger - You can now trigger many of the default Submit Actions based on the values provided in checkboxes and lists by visitors who are filling out forms on your sites. You can combine selections and positive and negative responses.
- Send Standard Message Save Action – this action provides integration with the Email Campaign Manager. This allows you to use the Email Campaign Manager’s standard messages to send emails. This action can personalize messages by including information provided by the visitor when filling out a form, and combine this with the personalization available in Standard Messages.
- Send SMS Save Action - The new Send SMS Save Action allows users to send SMS messages to visitors who fill out a form, and personalize this form based on information provided in the form.
- Send MMS Save Action - The new Send MMS Save Action allows users to send rich MMS messages (including images and links) to visitors who fill out a form, and personalize this form based on information provided in the form.
- Telephone field – a default field has been added which accepts only numbers and characters typically used in phone numbers such as “(“,” )”,” –“ and ”+”
- SMS/MMS Telephone field – a default field has been added which accepts only numbers and the “+” character. This is designed to support the Send SMS and Send MMS Save Actions.
- Role membership verification - The “Is User in Role” Form Verification enables you to trigger actions based on whether or not a user is a member of a role. This allows you to leverage Sitecore’s security model to enact complex business logic in order to target specific actions to specific customer groups.
- Credit Card sample form - The sample credit card form includes more features commonly featured during credit card verification, such as expiry dates and a CVV field.
- Other enhancements:
- Accessibility compliance - Web Forms for Marketers 2.1 is WCAG 2.0 level AA compliant. (320696)
- Form Reports for Oracle – The Dropout, Usability and Failure reports are now supported for Oracle.
- One button, no fields - Forms can now be comprised of a single submit button with no fields. This useful in cases where you want to provide actionable links which trigger complex actions on your site, especially in the case where the visitor is already authenticated.
Important changes:
- New security roles:
- Sitecore Marketer Form Author - this role inherits from the Sitecore Client Form Author, Analytics Maintaining and Analytics Reporting roles and allows corresponding form activities.
- The following Sitecore security roles are now utilized by Web Forms for Marketers module:
- Sitecore Client Developing
- Sitecore Client Form Author
- Analytics Maintaining
- Analytics Reporting
- Sitecore Client Securing
Issues resolved:
- Save Actions:
- A number of Save Actions use unique identifiers to identify users. An Email field is often used for this. You configure Sitecore to either allow or disallow the use of the “@” symbol. These Save Actions now detect the correct setting and escape email values only if the domain does not support the “@” symbol (325421)
- Dynamic links were not updated in the Send Mail Save Action (322386)
- If you create a new form by copying an existing one, some values in the Submit Actions from the original form were present in the new form, even if the actions in the new form were changed. (316482)
- Fields and validations:
- CAPTCHA voice replay for accessibility did not work in Windows 7 (326455)
- The File Upload field type did not support the Not Empty validator. This means that it didn’t fail if no file was uploaded. (325273)
- The count chars validator which validates the number of allowed characters in a field did not work accurately in Internet Explorer. (309829)
- The Date control did not work without analytics enabled (325919)
- Inserting and designing forms:
- The insert form wizard did not show placeholders which contains the “-”symbol in their names (313666)
- The insert form wizard did not show placeholders which contains whitespaces in their names (312161)
- The insert form wizard did not show placeholders in Preview mode (315504)
- Custom css classes were loaded before default css classes. This could lead to style problems (325271)
- The form field is now hidden if it does not contain a title (325420)
- Miscellaneous Issues:
- If you used the same FormsRoot for different sites, an exception occured. (324081)
- In the Form Reports application the column name was shown as the GUID of an item when the Title field is blank. This is now displayed as name of the item. (321757)
- The user profile field in the form template is now shared and unversioned (327105)
December 1, 2009
The Web Forms for Marketers module v2.0.0 rev.091120 is released.
Tested with Sitecore CMS 6.1.0 rev. 091029 (Update-3) and Sitecore CMS 6.2.0 rev.091012.
Change log.
New features:
- The User Exists Save Action now includes the ability to choose whether the action should fail if the user does not exist OR if the user already exists. The previous version only failed if the user does not exist.
- The Send Mail Save Action now allows you to select form field values from a drop down list to use in the To, CC and Subject fields. Previously you had to type in the values in the field in the form [Field Name].
Issues resolved:
- In the Form Reports, the following commands were not always displayed on the Ribbon: “All to Excel”, “All to Xml”, “Archive All”, “Delete All”, “Restore All”.
- The Create User Save Action failed with the error message “Root Element is missing” when using the default values in the Form Field and User Profile fields, in the Additional User Properties tab.
- In the Send Mail Save Action, adding a form field value using the insert field dropdown list might resulted in a script error.
- In the Send Mail Save Action, using the values of Upload File fields in the body of a mail resulted in an error, and the file was not displayed.
- Default error messages for a number of validations have been improved, in order to be more informative for the end user.
- Opening the Form Designer might cause an error in the log file.
- The values of Captcha fields were displayed in reports. Now they are hidden in the same way as Password and Credit Card fields.
- DropList field type had an incorrect default css value by default.
- Client CreditCard validation raised a script exception in IE8.
October 21, 2009
The Web Forms for Marketers module v2.0.0 rev.091016 is released.
Tested with Sitecore CMS 6.2.0 rev.091012.
Change log.
New features:
- Analytics and Reporting
- The module provides web analytics and reporting capabilities for forms, integrating with the capabilities of the Sitecore Online Marketing Suite (OMS).
- Form Submissions are tracked and can be used in conjunction with the Online Marketing Suite’s analytics capabilities.
- Forms can automatically be associated with goals, so that a successful form submission can be tracked using conversions, and profile values and other OMS analytics features can also be used.
- Forms can be associated with campaigns, so that a visitor will be included as a part of a campaign, if they have successfully submitted a given form.
- Visitor entries into form fields are tracked using AJAX technology. This allows tracking of abandoned forms (form dropouts) and enables form usability analysis.
- All validation errors and failures encountered on a form are tracked for every visitor.
- A Form Dropouts report is available in the Form Reports application, which tracks all instances where a form has been abandoned, or not successfully submitted.
- A Form Usability report is available in the Form Reports application, which details every form entry, error and failure, and final form result for every visitor, as well as the previous and next pages visited.
- A Save Failures report is available in the Form Reports application, which includes information of failed Save Actions associated with specific forms.
- The OMS session report has been extended to include form related events and entries.
- A property can be set on individual form fields which will include the value of the field in the OMS Tag information in the Analytics reports.
- Certain Save Actions allow you to associate a visitor with a Sitecore user based on the values of specific form fields.
- Certain Save Actions allow you to enter audit information if the Action has made changes based on the values of specific form fields.
- Field Properties
- A set of predefined validations has been provided to make it easier to set up basic validation on form fields.
- Field Types
- A new Captcha field type is available. This allows you to set different levels of noise and warping, and also has an audio playback feature for accessibility purposes.
- A new Credit Card field type is available, which has both Card Type and Card Number fields, and validations for the most common credit cards. For security reasons, the value of this field is never tracked or stored in the Analytics database.
- A new Password-Confirmation field type is available, which includes Password and Confirm Password fields. This replaces the Confirm-Password Submit Action in 6.2. For security reasons, the value of this field is never tracked or stored in the Analytics database.
- The module now supports using .ascx controls for field types. All the field types new to this version use .ascx.
- Submit Actions
- Submit Actions in earlier versions of the Web Forms for Marketers module are now called Save Actions.
- Web Forms for Marketers 2 introduces Form Verifications which is a new type of actions that return the visitor to the form field if the action fails.
- Default Form Verifications
- A User Exists Form Verification is available which verifies whether a User Exists based on the values of specific form fields.
- A Check User and Password Form Verification is available which validates a user based on the values of specific form fields.
- New Save Actions
- A Create User Save Action is available which creates a new Sitecore user or updates an existing one based on the values of specific form fields.
- An Edit Role Membership Save Action is available which adds and/or removes a Sitecore user from a role, or creates a new user, based on values of specific form fields.
- A User Login Save Action is available which logs a user in, based on the values of specific form fields.
- A User Login with password Save Action is available which validates and logs a user in based on the values of specific form fields.
- A Change Password Save Action is available which changes a user’s password based on the values of specific form fields.
- A Logout Save Action is available which logs a user out.
- A Register Conversion Save Action is available which registers a conversion for a selected goal, based on the value of a specific checkbox field.
- A Register Campaign Save Action is available which registers a visitor as a member of a selected campaign, based on the value of a specific checkbox field.
- Success Action
- If a form is successfully completed the visitor can be directed to a selected page, or a specific success message is displayed.
Improvements:
- The Send Mail action now allows the values of selected form fields to be used in the To, Cc and Subject fields.
- The Send Mail action now includes a Bcc field.
- A Read Query String property has been added which allows the form (Form Interpreter) to read initial values from a query string. This is accessible using the Design button in the Presentation tab.
Important changes:
- Submit Actions from earlier versions of Web Forms for Marketers are now split into Form Verifications and Save Actions. This is also reflected in the folder structure in the /sitecore/system/Modules/Web Forms for Marketers/Settings/Actions folder.
- The “Form Data Viewer” is now named “Form Reports” to more accurately reflect its purpose.
- A “Validation” property has been added to the Form Designer, which contains predefined validations for fields. A Regular expression property has been added which contains the regular expression used to validate the field.
- The Web Forms database has been changed from Sitecore.Webforms to Sitecore_Webforms. This is due to a change in the database structure, and in order to comply with MSSQL best practice.
- The formatSuccessMessage message pipeline has been replaced with the successAction pipeline.
- The processor type entry:<processor type="Sitecore.Form.Core.Pipelines.FormSubmit.ClearBrokenMedia, Sitecore.Forms.Core"/>has been moved from the errorSubmit pipeline to the errorSave pipeline.
Issues resolved:
- HTML produced by the Web Forms for Marketers module has been improved to comply with W3C and XHTML 1.0 guidelines.
- Conflict between Upload File field type and Send Mail action, resulting images not being properly displayed in the mail.
- Validation of number of characters does not work with 0 characters.
- Radio lists can now be made required fields.
- Export to Excel function now correctly produces XLS files.
2. Known issues
The following known issues are present in the Web Forms for Marketers 2.1.0 rev. 100806 or earlier.
Forms cannot be inserted when using Web Forms for Marketers 2.1.0 rev.100806 installed on CMS 6.3.0 rev.100830
Relates to: Web Forms for Marketers 2.1.0 rev.100920.
A Javascript error occurs when trying to insert a form in Web Forms for Marketers 2.1.0 rev.100806 installed on CMS 6.3.0 rev.100830. The error message is:
Workaround:
- Replace the Website\sitecore\shell\Applications\Modules\Web Forms for Marketers\InsertFormWizard.xml file with the attached one. Alternatively, edit the file manually according to the instructions below.
- Find the following script definitions:<Script runat="server" Src="Applications/Modules/Web Forms for Marketers/script/Utils.js"/>
<Script runat="server" Src="Applications/Modules/Web Forms for Marketers/script/Sitecore.PlaceholderManager.js"/> - Cut those definitions and paste them after the following line:<WizardForm Application="Modules/Web Forms for Marketers/Insert Form Wizard" CodeBeside="Sitecore.Forms.Shell.UI.InsertFormWizard, Sitecore.Forms.Core">
So the final version of the InsertFormWizard.xml file should look like this:
<Script runat="server" Src="controls/SitecoreModifiedHandling.js"/>
<Script runat="server" Src="controls/SitecoreVSplitter.js"/>
<Script runat="server" Src="controls/SitecoreWindow.js"/>
<Script runat="server" Src="controls/SitecoreKeyboard.js"/>
<Script runat="server" Src="Controls/Sitecore.Runtime.js"/>
<WizardForm Application="Modules/Web Forms for Marketers/Insert Form Wizard" CodeBeside="Sitecore.Forms.Shell.UI.InsertFormWizard, Sitecore.Forms.Core">
<Script runat="server" Src="Applications/Modules/Web Forms for Marketers/script/Utils.js"/>
<Script runat="server" Src="Applications/Modules/Web Forms for Marketers/script/Sitecore.PlaceholderManager.js"/>
JavaScript errors when using Web Forms for Marketers
Relates to: Web Forms for Marketers 2.1.0 rev.100920
If you are using webforms with Sitecore CMS 6.2.0 rev.100507 (Update 2), you may experience JavaScript errors when using Web Forms for Marketers. This will be fixed in Sitecore CMS 6.2.0 Update 3. Use this workaround to fix the issue.(330478)
Installation error
Relates to: Web Forms for Marketers 2.1.0 rev.100920
If you are upgrading from Web Forms for Marketers 2.0 using the Update Installation Wizard, you may encounter an installation error: “Error installing <package name>.” An exception occurred when installing the package. If you encounter this issue try to rename the package to a shorter name and install it again. If you still experience issues please contact Sitecore Customer Service via http://support.sitecore.net (using reference number 326481).
Export to excel file works incorrectly in Internet Explorer
Relates to: Web Forms for Marketers 2.1.0 rev.100920
In Internet Explorer, after converting a form report to an excel file, the file cannot be opened.
Workaround: Turn off the Internet Explorer Information bar. See this page ("Can I turn off the Information bar" section) for the detailed instructions.
Form events used for Form Dropout tracking are not entered into the Analytics database, causing the Dropout and Usability Reports to be empty.
Relates to: Web Forms for Marketers 2.1.0 rev.100806.
This issue is present in Web Forms for Marketers 2.1 rev. 100806 (Update 2) when using Sitecore CMS 6.1 or 6.2.
If dropout tracking is enabled for a form, the related dropout events are not correctly written into the Analytics database. This also causes an exception in the log file. This means that every time the visitor enters a form value into the form and does not successfully submit the form, it is not tracked. This causes the Dropout and Usability Forms to be empty. This has no effect on the statistical Data and Summary information. This is not an issue which is relevant for customers who do not use Form Dropout tracking or do not have the Online Marketing Suite (OMS) enabled.
Workaround: Add the Newtonsoft.Json.dll library to the Windows assembly (GAC) for .NET version 3.5 to GAC.
Web Forms for Marketers 2.1.0 rev. 100629 and earlier versions are not compatible with Sitecore CMS 6.3
Relates to: Web Forms for Marketers 2.1.0 rev.100629.
Web Forms for Marketers 2.1.0 rev. 100629 and earlier versions are not compatible with Sitecore CMS 6.3.
Web Forms for Marketers 2.1.0 rev. 100629 requires that the form tag ID in the layout is called "mainform"
Relates to: Web Forms for Marketers 2.1.0 rev.100629
Forms are not correctly submitted if the id of the form tag in the layout is not “mainform”.
Web Forms placed on the cached sublayouts don't work.
Reference number: 354946
Web Forms placed on the sublayouts with the enabled caching do not work. It is an expected behavior. When the cached sublayout is requested Sitecore returns the cached HTML output omitting the usual ASP.NET web control life cycle. For more information about the Output Caching in Sitecore CMS, see Presentation Component Reference.
Workaround: Disable caching for sublayouts containing the web form.